• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

The response from a URL protected by Cloudflare may only provide a relevant cookie on the first response but #curl_http_content_headers_and_checksum only returns the headers of the final response. In this scenario, #curl_check_http_content isn't able to properly detect the protected URL and this is surfaced as an error instead of skipping the URL (see Homebrew/homebrew-cask#124277).

This PR resolves the issue by including the array of response hashes in the return value from #curl_http_content_headers_and_checksum, so we can check all the responses in #curl_check_http_content.

Besides that, this also renames the :status key in the return hash from #curl_http_content_headers_and_checksum to :status_code. This aligns the key name with the return hash from #parse_curl_response and technically allows us to pass either hash to the #url_protected_by_* methods (as they both contain :status_code and :headers in the expected format. This felt like a nicer way of approaching the switch from the details hash to a response hash.